1. Home
  2. Vulnerabilities
  3. CVE-2022-49350
0.0
NA
CVE-2022-49350
Linux Kernel net mdio EXPORT_SYMBOL Uninitialized Memory Access Vulnerability
Description

In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)

INFO

Published Date :

Feb. 26, 2025, 7:01 a.m.

Last Modified :

Feb. 26, 2025, 7:01 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-49350 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Update the Linux kernel to a version that includes the fix for mdio_bus_init.
  • Update the Linux kernel to the latest stable version.
  • Ensure the kernel is compiled with appropriate configurations.
  • Reboot the system after the kernel update.
  • Verify the integrity of the system after reboot.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2022-49350.

URL Resource
https://git.kernel.org/stable/c/35b42dce619701f1300fb8498dae82c9bb1f0263
https://git.kernel.org/stable/c/5534bcd7c40299862237c4a8fd9c5031b3db1538
https://git.kernel.org/stable/c/59fa94cddf9eef8d8dae587373eed8b8f4eb11d7
https://git.kernel.org/stable/c/6a90a44d53428a3bf01bd80df9ba78b19959270c
https://git.kernel.org/stable/c/7759c3222815b945a94b212bc0c6cdec475cfec2
https://git.kernel.org/stable/c/ab64ec2c75683f30ccde9eaaf0761002f901aa12
https://git.kernel.org/stable/c/f2f0f8c18b60ca64ff50892ed899cf1c77864755
https://git.kernel.org/stable/c/f5c68137f1191ba3fcf6260ec71b30be2e2bf4c3
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2022-49350 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2022-49350 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-49350 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2022-49350 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Feb. 26, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)
    Added Reference https://git.kernel.org/stable/c/35b42dce619701f1300fb8498dae82c9bb1f0263
    Added Reference https://git.kernel.org/stable/c/5534bcd7c40299862237c4a8fd9c5031b3db1538
    Added Reference https://git.kernel.org/stable/c/59fa94cddf9eef8d8dae587373eed8b8f4eb11d7
    Added Reference https://git.kernel.org/stable/c/6a90a44d53428a3bf01bd80df9ba78b19959270c
    Added Reference https://git.kernel.org/stable/c/7759c3222815b945a94b212bc0c6cdec475cfec2
    Added Reference https://git.kernel.org/stable/c/ab64ec2c75683f30ccde9eaaf0761002f901aa12
    Added Reference https://git.kernel.org/stable/c/f2f0f8c18b60ca64ff50892ed899cf1c77864755
    Added Reference https://git.kernel.org/stable/c/f5c68137f1191ba3fcf6260ec71b30be2e2bf4c3
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.